Skip to content

handle 'exit' message #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

extemporalgenome
Copy link

At least with the helix editor, prior to this change,
golangci-lint-langserver will handle the 'shutdown' message,
but will then stall, waiting for the invoking client (helix)
to terminate the LSP process, while helix is waiting for the LSP process
to self-terminate upon receiving the 'exit' message.
Eventually, helix will terminate the LSP process
after a ~10 second grace period has passed,
though this is rather annoying to wait for.

With the change, the 'exit' command will cause
the jsonrpc2 connection to close,
which in turn will lead to the LSP process exiting quickly.

At least with the helix editor, prior to this change,
golangci-lint-langserver will handle the 'shutdown' message,
but will then stall, waiting for the invoking client (helix)
to terminate the LSP process, while helix is waiting for the LSP process
to self-terminate upon receiving the 'exit' message.
Eventually, helix will terminate the LSP process
after a ~10 second grace period has passed,
though this is rather annoying to wait for.

With the change, the 'exit' command will cause
the jsonrpc2 connection to close,
which in turn will lead to the LSP process exiting quickly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant